-
Notifications
You must be signed in to change notification settings - Fork 3
Add browser use guide #52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add browser use guide #52
Conversation
Added browser user integration guide to docs. It includes a guide for integrating into an existing browser use implementation as well as starting from scratch with our app template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Performed full review of 67a3532...9949471
Analysis
- The OpenAPI snippet updates appear to be automated regeneration - ensure these changes are intended and properly validated
- New proxy-related endpoints are being added, which expands the API surface area - consider if this expansion needs additional security review or documentation
- Integration maintains compatibility with existing code but may introduce dependencies on Kernel's cloud infrastructure that should be clearly communicated to users
Tip
⚡ Quick Actions
This review was generated by Mesa.
Actions:
Slash Commands:
/review- Request a full code review/review latest- Review only changes since the last review/describe- Generate PR description. This will update the PR body or issue comment depending on your configuration/help- Get help with Mesa commands and configuration options
9 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings
juecd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 comment + could you double check the proxy additions in this commit are intentional?
| ) | ||
| client.browsers.delete_by_id( | ||
| "id", | ||
| "htzv5orfit78e1m2biiifpbv", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nope - wondering if that's from Hiro's work? I didn't change that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ohhh good call
| @@ -0,0 +1,23 @@ | |||
| <CodeGroup> | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this from another commit that's not yet in main?
Updated to UV method and included dependency name.
Simplified to use uv add instead of two steps
Updated kernel import
To avoid confusion, changing name of class to client instead of the package name kernel
Added browser user integration guide to docs. It includes a guide for integrating into an existing browser use implementation as well as starting from scratch with our app template.
Implementation Checklist
Testing
mintlify devworks (see installation here)Visual Proof
TL;DR
Adds a new guide for integrating Kernel's Browser APIs into automation scripts.
Why we made these changes
To provide developers with a clear guide for integrating our Browser APIs, covering both starting a new project from our template and adding it to an existing implementation.
What changed?
integrations/browser-use.mdx, a new guide for using Kernel with browser automation.create-kernel-apptemplate.create,list,retrieve,delete).Description generated by Mesa. Update settings